Data feeds of consumer eSIMS for a subscription management service

ABSTRACT

One or more consumer Embedded Subscriber Identity Module (eSIM) profiles that are provided by at least one eSIM profile vendor may be received at a subscription management service of a wireless communication carrier. The one or more consumer eSIM profiles are loaded into a Subscription Manager Data Preparation Plus (SM-DP+) profile data store of the subscription management service, each consumer eSIM profile for deployment to an eUICC in a consumer device. At least one corresponding Integrated Circuit Card identifier (ICCID) of the one or more consumer eSIM profiles as loaded into the SM-DP+ data store is then sent via the subscription management service to an eSIM profile management platform of the wireless communication carrier using a service data feed, in which the eSIM profile management platform provides a central interface for a plurality of entities to perform actions with respect to multiple eSIM profiles and multiple eUICC Identifiers (EIDs).

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

This patent application is a divisional application of U.S. patentapplication Ser. No. 15/816,713, filed on Nov. 17, 2017, entitled“Subscription Management Service Data Feeds,” which claims priority toU.S. Provisional Patent Application No. 62/535,192, filed on Jul. 20,2017, entitled “Subscription Managers,” which is hereby incorporated byreference in its entirety.

BACKGROUND

The use of Embedded Universal Integrated Circuit Cards (eUICCs), alsoreferred to as Embedded Subscriber Identity Modules (eSIMs), arebecoming increasingly prevalent in consumer and machine-to-machine (M2M)communication fields. Unlike a traditional UICC or SIM card that existsas a removable smart card that is transferrable between multipledevices, an eUICC is an integrated circuit that is not designed to beuser removable, i.e., it is generally embedded with or soldered to otherelectronic components of a device.

An eUICC may be provisioned with one or more eSIM profiles, in whicheach eSIM profile contains a unique international mobile subscriberidentity (IMSI) number that authenticates a subscriber to a wirelesscommunication carrier. Other data that are stored in the eSIM profilemay include carrier network information, security authenticationinformation, a list of accessible network services, and/or so forth. Thewireless communication carrier may transfer an eSIM profile to the eUICCof a user device in the form of a consumer device or a M2M device via anover-the-air (OTA) update. Consumer devices are network-capable devicesthat are generally marketed to individual consumers. For example, thesedevices may include a smartphone, a tablet computer, a smartwatch, agaming console, and/or so forth. M2M devices are networked machines thatuse the telecommunication services provided by the wirelesscommunication carrier to communicate with other networked machines. Forexample, a M2M monitoring device that is embedded on a vehicle mayautomatically send vehicle tracking and operation information to aremote support device at a control center. In another example, a M2Mdevice in the form of a smart home appliance may automatically senddiagnostic information to a monitoring device at a service center incase of device malfunction.

In order to provide eUICCs of user devices with eSIM profiles, awireless communication carrier has to purchase or otherwise obtain theeSIM profiles from eSIM profile vendors. An eSIM profile vendor may be amanufacturer of eUICCs, and thus is able to generate eSIM profiles forinstallation in the eUICCs. Accordingly, the wireless communicationcarrier may place an order for a set of eSIM profiles for an eSIMprofile vendor. The eSIM profile vendor then transfers the set of eSIMprofiles to a profile data store of a subscription management service ofthe wireless communication carrier. Following the arrival of the set ofeSIM profiles in the profile data store, an eSIM profile managementplatform of the may receive requests to provide specific eSIM profilesfrom the set of eSIM profiles to particular eUICCs. The requests mayoriginate from a business support system (BSS) of the wirelesscommunication carrier, BSSs of other wireless communication carriersthat are hosted by the wireless communication carrier, or partnerservice or content providers of the wireless communication carrier. Inturn, the eSIM profile management platform is responsible for triggeringthe subscription management service to distribute eSIM profiles toeUICCs of user devices. However, in some scenarios, the eSIM profilemanagement platform may receive a request to distribute an eSIM profileto an eUICC even before an eSIM profile has arrived at the profile datastore of the subscription management service. In such scenarios, thesubscription management service may fail to distribute the eSIM profileto the eUICC after being directed by the eSIM profile managementplatform, but the cause of such an error may not be immediatelyapparent.

In other scenarios where there are multiple subscription managementservices that interfaces with an eSIM profile management platform,incoming ordered eSIM profiles that are intended to be stored in theprofile data store of a first subscription management service may beaccidentally routed to the profile data store of a second subscriptionmanagement service. In such a scenario, the misrouted eSIM profiles maybecome lost unless an audit is performed by an administrator of thesubscription management service to identify these lost profiles.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures, in which the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 illustrates an example architecture that enables the provision ofservice data feeds by subscription management services to an eSIMprofile management platform.

FIG. 2 illustrates an operating environment that enables the eSIMmanager platform to perform error reporting and eSIM profile accesscontrol based on the service data feeds provided by the subscriptionmanagement services.

FIG. 3 is a block diagram showing various components of one or moreillustrative computing devices that support the provision of servicedata feeds by subscription management services to an eSIM profilemanagement platform.

FIG. 4 is a flow diagram of an example process for receiving servicedata feeds for M2M devices from a subscription management service.

FIG. 5 is a flow diagram of an example process for receiving servicedata feeds for consumer devices from a subscription management service.

FIG. 6 is a flow diagram of an example process for using the servicedata feed information from subscription management services to controlaccess to eSIM profiles that are stored in a profile data store of asubscription management service.

FIG. 7 is a flow diagram of an example process for using the servicedata feed information from subscription management services to controlaccess to M2M eUICC Identifiers (EIDs) that are stored in an EID datastore of a subscription management service.

DETAILED DESCRIPTION

This disclosure is directed to techniques that enable an eSIM profilemanagement platform of a wireless communication carrier to receiveservice data feeds from multiple subscription management services. Eachof the multiple subscription management services is responsible for themanagement of one or more sets of eSIM profiles that are provisioned toeUICCs of particular user devices. A set of eSIM profiles managed byeach subscription management service may belong to one or more specificentities, such as a wireless communication carrier, or multiple wirelesscommunication carriers. In another example, the one or more specificentities may include third-party partner of a wireless communicationcarrier, or multiple third-party partners of the wireless communicationcarrier. A third-party partner of the wireless communication carrier maybe a provider that provides content or services to the subscribers ofthe carrier, a M2M device vendor, a M2M device operator, and/or soforth. Each of the subscription management services may be provided byone or more subscriber managers. In some embodiments, each of thesubscription management services may be provided by at least oneSubscription Manager Data Preparation (SM-DP), at least one SubscriptionManager Data Preparation Plus (SM-DP+), and at least one SubscriptionManager Secure Routing (SM-SR).

The eSIM profile management platform is a backend service of a wirelesscommunication carrier that serves as a central interface between thevarious entities and the subscription management services. The eSIMprofile management platform enables these entities to manage eSIMprofiles for deployment into eUICCs of user devices. For example, theeSIM profile management platform may receive a request from an entity toprovision an eUICC of a user device with an eSIM profile, activate aneSIM profile that is stored in the eUICC for use, or delete an eSIMprofile from the eUICC. In turn, the eSIM profile management platformmay relay the request to the appropriate subscription management serviceof the multiple subscription management services that is responsible formanaging the affected eSIM profile. Following the completion of therequest, the eSIM profile management platform may provide a notificationto the entity indicating that the request has been fulfilled.

In various embodiments, a subscription management service may receiveeSIM profiles from an eSIM profile vendor. Since an eSIM profile vendormay be a manufacturer of eUICCs, the eSIM profile vendor is alsoreferred to as an eSIM manufacturer (EUM). A subscription managementservice may load the received eSIM profiles into profile data stores.For example, eSIM profiles for M2M devices may be loaded into profiledata stores of SM-DPs. Along with the loading of these eSIM profiles forM2M devices, the eSIM profile vendor also provides eUICC Identifiers(EIDs) of eUICCs that are for use by M2M devices. Such EIDs are loadedinto a data store of a SM-SR. On the other hand, eSIM profiles forconsumer devices may be loaded into profile state stores of a SM-DP+.

Following the loading of the eSIM profiles and the EIDs, thesubscription management service may provide service data feeds to theeSIM profile management platform. For example, the service data feedsmay include Integrated Circuit Card identifiers (ICCIDs) of the eSIMprofiles that are loaded into the profile data stores of the SM-DPs andthe SM-DP+. The ICCID for an eSIM profile that is contained in a servicedata feed may be accompanied by other associated identificationinformation, such as a mobile network operator (MNO) identifier, asubscription management service identifier, a partner identifier, and/oran EUM identifier. The MNO identifier identifies the wirelesscommunication carrier associated with the eSIM profile, in which thewireless communication carrier has access to the eSIM profile. Thesubscription management service identifier identifies a responsiblesubscription management service that has the authority to manage theeSIM profile. The partner identifier identifies a third-party partner ofa wireless communication carrier that has access to the eSIM profile,and the eNUM identifier identifies the eSIM profile vendor that issuedthe eSIM profile.

The service data feeds may further include the EIDs of the eUICCs forM2M devices. The EID for an eUICC that is contained in the service datafeed may also be accompanied by other associated identificationinformation, such as a MNO identifier, a partner identifier, asubscription management service identifier, and/or an EUM identifier ina similar manner. In turn, the eSIM profile management platform maystore the identification information obtained from the service datafeeds in a data fee store.

The eSIM profile management platform may use the identificationinformation from the service data feeds to regulate the activities ofvarious entities with respect to the eSIM profiles. For example, anentity may send to the eSIM profile management platform a request toprovision an eUICC of a user device with a particular eSIM profile. Inturn, the eSIM profile management platform may use the ICCID of the eSIMprofile to determine whether a responsible subscription managementservice has actually received the eSIM profile from an eSIM profilevendor for storage in a profile data store. If the subscriptionmanagement service has received and stored the eSIM profile in a profiledata store, the eSIM profile management platform may determine whetherthe entity has access to the subscription management service. Assumingthat the entity has access to the subscription management service, theeSIM profile management platform may further compare the MNO identifieror the partner identifier associated with eSIM profile to the entityidentifier of the entity to determine whether the entity has access tothe eSIM profile. Thus, when there is a match between the identifiers,the eSIM profile management platform may forward the request of theentity to the responsible subscription management service, such that theeUICC of the user device may be provisioned with the particular eSIMprofile. Otherwise, the eSIM profile management platform may notify theentity that the request of the entity has failed.

The ability of the eSIM profile management platform to receive servicedata feeds from multiple subscription management services allows theeSIM profile management platform to regulate access by various entitiesto the eSIM profiles managed by the services. The identificationinformation in the data feeds may be used by the platform to preventunauthorized access by an entity to a subscription management service,unauthorized access by a first entity to eSIM profiles that are orderedby a second entity. The data feeds may also reveal issues such as lateor failed transmissions of eSIM profiles to a subscription managementservice, or eSIM profiles being mistakenly transmitted to and stored bythe wrong subscription management service. The techniques describedherein may be implemented in a number of ways. Example implementationsare provided below with reference to the following FIGS. 1-7.

Example Architecture

FIG. 1 illustrates an example architecture 100 that enables theprovision of service data feeds by subscription management services toan eSIM profile management platform. The wireless communication carrier102 may provide a wide range of mobile communication services, as wellas ancillary services and features, to subscribers and associated mobiledevice users. The wireless communication carrier 102 may also bereferred to as a mobile network operator (MNO). In various embodiments,the wireless communication carrier 102 may provide wirelesscommunication between multiple user devices. Further, the wirelesscommunication carrier 102 may also provide communications between themultiple user devices and user devices that are serviced by othertelecommunications networks. The telecommunication services provided mayinclude voice communication, multimedia communication, datacommunication, such as email, messaging, content streaming, contentuploading, and/or so forth.

The wireless communication carrier 102 may be implemented using multipleinterconnected networks. In various embodiments, the wirelesscommunication carrier 102 may include multiple Radio Access Networks(RANs). The RANs may be connected to each other via regional groundnetworks. In turn, the regional ground networks may be connected to acore network by a wide area network (WAN). Each regional portion of thewireless communication carrier 102 may include one or more RANs and aregional circuit and/or packet switched network and associated signalingnetwork facilities. The wireless communication carrier 102 may providetelecommunication services in accordance with one or more technicalstandards, such as Enhanced Data Rates for GSM Evolution (EDGE),Wideband Code Division Multiple Access (W-CDMA), High Speed PacketAccess (HSPA), Long Term Evolution (LTE), CDMA-2000 (Code DivisionMultiple Access 2000), 5th Generation (5G), and/or so forth. In someembodiments, the core network of the wireless communication carrier 102may be accessed via wired or wireless local area networks (LANs). Forexample, a wireless local area network may be a network that isestablished using Wi-Fi or Bluetooth standards and hardware.

A RAN of the wireless communication carrier 102 may include a number ofbase stations, also referred to as network cells. In some embodiments,the base stations may be in the form of nodes. Each node may include abase transceiver system (BTS) that communicates via an antennae systemover an air-link with one or more user devices that are within range.The BTS may send radio communication signals to user devices and receiveradio communication signals from user devices. The RANs may carry thecommunications of the user devices between the respective base stationsand a core network of the wireless communication carrier 102. The corenetwork may connect to a public packet data communication network, suchas the Internet. Data and voice communications via the RANs, the corenetwork, and the Internet may support a variety of telecommunicationservices through the wireless communication carrier 102.

In various embodiments, 2G and/or 3G network components of the wirelesscommunication carrier 102 may include a serving GPRS support node (SGSN)that routes voice calls to and from the public switched telephonenetwork (PSTN), a Gateway GPRS Support Node (GGSN) that handles therouting of data communication between external packet switched networksand the core network. The network components may further include aPacket Data Network (PDN) gateway (PGW) that routes data traffic betweenthe GGSN and the Internet. The LTE components of the wirelesscommunication carrier 102 may include an Evolved Packet Core (EPC) andan IP Multimedia Subsystem (IMS) core.

The wireless communication carrier 102 may provide telecommunicationservices to multiple user devices, which may include consumer devicesand M2M devices. Consumer devices are network-capable devices that aregenerally marketed to individual consumers, and are capable of obtainingtelecommunication and/or data communication services from the wirelesscommunication carrier 102. For example, these devices may include asmartphone, a tablet computer, a smartwatch, a gaming console. M2Mdevices are networked machines that use the telecommunication servicesprovided by the wireless carrier to communicate with other devices. Eachof the user devices may be equipped with an eUICC, i.e., an integratedcircuit chip that is directly wired or soldered to a circuit board ofthe user device. The eUICC may store one or more eSIM profiles, such asthe eSIM profile 112(1). Each eSIM profile may include information foraccessing telecommunication services provided by a correspondingwireless communication carrier, such as the wireless communicationcarrier 102. Each user device may be further equipped with a modem thatenables the user device to perform telecommunication and datacommunication with the wireless communication carrier 102. Accordingly,the modem may encode digital information for transmission in uplinkradio signals to the wireless communication carrier 102, as well asdecode digital information that are received from the wirelesscommunication carrier 102 via downlink radio signals.

A user device may receive eSIM profiles for storage on the eUICC viaover-the-air (OTA) updates from wireless communication carriers. Forexample, a subscription management service, such as the subscriptionmanagement service 104, may send one or more data packets that containan eSIM profile to the modem of the user device via downlinkcommunication. The data packets are assembled by the software of themodem into the eSIM profile and sent to the eUICC for installation inthe eUICC.

The backend servers of the wireless communication carrier 102 mayprovide an eSIM profile management platform 106. The eSIM profilemanagement platform 106 may serve as a central interface between thevarious entities and one or more subscription management services, suchas the subscription management services 104(1)-104(N). In variousembodiments, the eSIM profile management platform 106 may be anapplication program interface (API) abstraction layer that providesmultiple APIs to the various entities, in which the entities may callthe APIs to perform specific tasks. Accordingly, the eSIM profilemanagement platform 106 enables these entities to manage eSIM profilesfor deployment into eUICCs of user devices. Each of the subscriptionmanagement services 104(1)-104(N) is responsible for the management ofone or more sets of eSIM profiles that are provisioned to eUICCs ofparticular user devices. A set of eSIM profiles managed by eachsubscription management service may belong to one or more specificentities, such as the wireless communication carrier 102, or anassociated wireless communication carrier that is hosted by wirelesscommunication carrier 102. In another example, the one or more specificentities may include a third-party partner of a wireless communicationcarrier 102, or multiple third-party partners of the wirelesscommunication carrier 102. A third-party partner of the wirelesscommunication carrier may be a provider that provides content orservices to the subscribers of the carrier, a M2M device vendor, a M2Mdevice operator, and/or so forth. Each of the subscription managementservices 104(1)-104(N) may be provided by one or more subscribermanagers. In some embodiments, each of the subscription managementservices 104(1)-104(N) may be provided by at least one SubscriptionManager Data Preparation (SM-DP), at least one Subscription Manager DataPreparation Plus (SM-DP+), and at least one Subscription Manager SecureRouting (SM-SR).

In its role as the central interface, the eSIM profile managementplatform 106 may receive a request from an entity to provision an eUICCof a user device with an eSIM profile, delete an eSIM profile from theeUICC, activate an eSIM profile that is stored in the eUICC for use toobtain communication services from a wireless communication carrier. Inturn, the eSIM profile management platform 106 may relay the request tothe appropriate subscription management service of the multiplesubscription management services that is responsible for managing theaffected eSIM profile. Following the completion of the request, the eSIMprofile management platform may provide a notification to the entityindicating that the request has been fulfilled.

In operation, a subscription management service, such as thesubscription management service 104(1), may receive eSIM profiles fromone or more eSIM profile vendors 108(1)-108(N). An eSIM profile vendormay transmit the eSIM profiles to the subscription management service104 over a communication link that is established between the vendor andthe service. For example, the eSIM profiles may be delivered to thesubscription management service 104(1) in response to an eSIM profileorder from the wireless communication carrier 102. However, in someinstances, the eSIM profile order may be initiated by another entity,such as a wireless communication carrier that is hosted by the wirelesscommunication carrier 102, or a third-party partner of the wirelesscommunication carrier 102. The hosted wireless communication carrier maybe a mobile virtual network operator (MVNO), a virtual network operator(VNO), or a mobile other licensed operator (MOLO). In such instances,the wireless communication carrier 102 may not be aware that the orderfor the eSIM profiles has been placed by the entity. The eSIM profilesthat are received by the subscription management service 104(1) mayinclude eSIM profiles for M2M devices and eSIM profiles for consumerdevices.

The eSIM profiles for M2M device, also referred to as M2M eSIM profiles,may be loaded into the profile data stores of SM-DPs 110(1)-110(N). Invarious instances, the profile data stores of each of the SM-DPs110(1)-110(N) may hold M2M eSIM profiles that are ordered by a singleentity or different entities. For example, a profile data store of theSM-DP 110(1) may hold the M2M eSIM profiles for the wirelesscommunication carrier 102, a profile data store of the SM-DP 110(2) mayhold the M2M eSIM profiles for a wireless communication carrier that ishosted by the wireless communication carrier 102, while a profile datastore of the SM-DP 110(N) may hold the M2M eSIM profiles for athird-party partner of the wireless communication carrier 102. Inanother example, a profile data store of the SM-DP 110(1) may hold theM2M eSIM profiles for the wireless communication carrier 102, but aprofile data store belonging to each of the SM-DP 110(2) and 110(N) mayhold the M2M eSIM profiles for a respective third-party partner of thewireless communication carrier 102. Thus, as shown in FIG. 1, the eSIMprofile vendor 108(1) may transmit a M2M eSIM profile 112(1) to theSM-DP 110(1), and transmit a M2M eSIM profile 112(2) to the SM-DP110(N). Further, the eSIM profile vendor 108(N) may transmit a M2M eSIMprofile 114 to the SM-DP 110(2). However, in other instances, a profiledata store of a SIM-DP may be configured to hold M2M eSIM profiles ofmultiple entities.

Along with the loading of the M2M eSIM profiles into one or more SM-DPs,the eSIM profile vendor also provides eUICC ID (EIDs) of eUICCs that arefor use by the M2M devices. Accordingly, the M2M eSIM profiles may beeventually deployed on these eUICCs. Such EIDs, referred to as M2M EIDs,are loaded into a data store of the SM-SR 116. For example, as shown inFIG. 1, the eSIM profile vendor 108(1) may transmit the M2M EID 118(1)and M2M EID 118(2) to a data store of the SM-SR 116. Likewise, the eSIMprofile vendor 108(2) may transmit an M2M EID 120 to the SM-SR 116.

On the other hand, the eSIM profiles for consumer devices, also referredto as consumer eSIM profiles, may be loaded into profile state stores ofa SM-DP+, such as the SM-DP+ 122. In some instances, each profile datastore of the SM-DP+ 122 may hold consumer eSIM profiles of a singleentity. In other instance, a single profile data store of the SM-DP+ 122may hold eSIM profiles of multiple different entities. For example, asshown in FIG. 1, the eSIM profile vendor 108(1) may transmit a consumereSIM profile 124 to the SM-DP+ 122. Likewise, the eSIM profile vendor108(2) may transmit a consumer eSIM profile 124 to the SM-DP+ 126.Further, while the subscription management service 104(1) is illustratedas having a single SM-DP+ 122, the service may be configured withmultiple SM-DP+s in other embodiments. In such embodiments, each SM-DP+is responsible for managing the consumer eSIM profiles of a differententity, or the multiple SM-DP+s can collectively manage consumer eSIMprofiles of a single entity.

The loading of the eSIM profiles and the M2M EIDs into the data storesof the subscription management service 104(1) may trigger a data feedfunction 128 of the service to provide service data feeds 130 to theeSIM profile management platform 106. For example, the service datafeeds may include Integrated Circuit Card identifiers (ICCIDs) of theeSIM profiles that are loaded into the profile data stores of the SM-DPsand the SM-DP+. The ICCID for an eSIM profile that is contained in aservice data feed may be accompanied by other associated identificationinformation, such as a mobile network operator (MNO) identifier, asubscription management service identifier, a partner identifier, and/oran EUM identifier. The MNO identifier identifies the wirelesscommunication carrier associated with the eSIM profile, in which thewireless communication carrier has access to the eSIM profile. Thesubscription management service identifier identifies a responsiblesubscription management service that has the authority to managing theeSIM profile. The partner identifier identifies a third-party partner ofa wireless communication carrier that has access to the eSIM profile,the EUM identifier identifies the eSIM profile vendor that issued theeSIM profile. In some instances, the service data feeds may furtherinclude an identifier of the specific SM-DP or SM-DP+ whose profile datastore actually stored each eSIM profile, and/or an indicator of whetherthe eSIM profile is a M2M eSIM profile or a consumer eSIM profile.

The service data feeds may further include the M2M EIDs of the eUICCsfor the M2M devices that are loaded into an EID data store of a SM-SR.The M2M EID for an eUICC that is contained in the service data feed mayalso be accompanied by other associated identification information, suchas a MNO identifier, a partner identifier, a subscription managementservice identifier, an SM-SR identifier, and/or an EUM identifier in asimilar manner. In some embodiments, these identifiers of each eSIMprofile or each M2M EID may be assigned by a corresponding eSIM profilevendor that provided the eSIM profile or M2M EID.

In some embodiments, the data feed function 128 of the subscriptionmanagement service 104(1) may provide the service data feeds afterreceiving each batch of eSIM profiles or EIDs from an eSIM profilevendor. For example, the data feed function 128 may provide a servicedata store after receiving a batch of M2M eSIM profiles, a batch ofconsumer eSIM profiles, or a batch of M2M EIDs. In other embodiments,the data feed function 128 may periodically provide service data feedsthat contains information on eSIM profiles that are newly received atregular time intervals (e.g., every minute, every five minutes, everyhour, etc.). This means that a service data feed may contain informationfor a mixture of M2M eSIM profiles, consumer eSIM profiles, and/or M2MEIDs. The service data stores are transmitted by the subscriptionmanagement service 104(1) via a communication link to the eSIM profilemanagement platform 106. The subscription management service 104(1) mayprovide the data feeds to the eSIM profile management platform 106 viavarious protocols and formats. The protocols may include Simple ObjectAccess Protocol (SOAP), Representational State Transfer (REST), and/orso forth, and the formats may include Hypertext Markup Language (HTML),Extensible Markup Language (XML), JavaScript Object Notation (JSON),and/or so forth.

In turn, the eSIM profile management platform 106 may store theinformation obtained from the service data feeds in a centralizeddatabase 132. Accordingly, the centralized database 132 is used by theeSIM profile management platform 106 to track the ICCID of each eSIMprofile that has been loaded, the specific subscription managementservice that is responsible for managing each loaded eSIM profile oreach loaded M2M EID, an identity of the specific SM-DP or SM-DP+ whosedata store holds each loaded eSIM profile, an identity of the specificSM-SR whose data store holds each loaded M2M EID. The centralizeddatabase 132 further contains data that indicates an identity of thewireless communication carrier and/or an identity of the third-partypartner that has access to each loaded eSIM profile or M2M EID. Invarious embodiments, the subscription management services 104(2)-104(N)may provide service data feeds regarding the eSIM profiles and M2M EIDsthat they receive from the eSIM profile vendors 108(1)-108(N) in asimilar manner as the subscription management service 104(1). In turn,the information from these data feeds are also stored in the centralizeddatabase 132 in the same manner as described above. As further discussedwith respect to FIG. 2 below, the eSIM profile management platform 106may use the identification information in the service data feedsreceived from the subscription management services 104(1)-104(N) toregulate the activities of various entities with respect to the eSIMprofiles.

Example Operating Environment

FIG. 2 illustrates an operating environment 200 that enables the eSIMprofile management platform 106 to perform error reporting and eSIMprofile access control based on the service data feeds provided by thesubscription management services. The operating environment 200 includesthe eSIM profile management platform 106 that is operated by a wirelesscommunication carrier 102. The eSIM profile management platform 106provides a central interface for multiple entities to perform actionswith respect to the eSIM profiles that are stored in the profile datastores of the subscription management services 104(1)-104(N). Forexample, the actions may include sending an eSIM profile for storage inan eUICC of a user device, activating an eSIM profile for use to receivetelecommunication services from the wireless communication carrier,disabling an eSIM profile to terminate access of the user device to thetelecommunication services, or deleting the eSIM profile from the eUICCof the user device. As shown in FIG. 2, the eUICC may be one of theeUICCs 202(1)-202(N) that resides in the user devices 204(1)-204(N). Themultiple entities may include the wireless communication carrier 102 oranother wireless communication carrier that is hosted by the carrier102. For example, the wireless communication carrier 102 may interactwith the eSIM profile management platform 106 via its BSS 206. Likewise,the hosted wireless communication carrier may interact with the eSIMprofile management platform 106 via its BSS 208. The multiple entitiesmay further include third-party partners, such as third-party partners210(1)-210(N) that interact with the eSIM profile management platform106 via respective eSIM management applications. In some embodiments,the subscription management services 104(1)-104(N) may be configured toreceive action requests solely from the eSIM profile management platform106, rather than individual entities. Such a configuration maystreamline the deployment and operation of the subscription managementservices 104(1)-104(N), as well as enhance network security because allaction requests are funneled through a trusted platform.

The eSIM profile management platform 106 may use the informationcontained in the service data feeds 130 to regulate the activities ofvarious entities with respect to the eSIM profiles. For example, anentity may send to the eSIM profile management platform 106 a request212 to provision the eUICC 202(N) of the user device 204(N) with aparticular eSIM profile 214, in which the request includes an ICCID ofthe eSIM profile 214 and an entity identifier of the entity. In turn,the eSIM profile management platform 106 may input the ICCID of the eSIMprofile 214 into the centralized database 132 to determine whether aresponsible subscription management service has reported that itactually received the eSIM profile 214 from an eSIM profile vendor. Ifthe centralized database 132 shows that a subscription managementservice, such as the subscription management service 104(N), has storedthe eSIM profile 214 into its profile data store, the eSIM profilemanagement platform may use the entity identifier of the entity todetermine whether the entity has access to the subscription managementservice 104(N). For example, a permission list maintained by the eSIMprofile management platform 106 for the subscription management service104(N) may indicate that the BSS 206(1) of a first wirelesscommunication carrier 106 has permission to access the subscriptionmanagement service 104(N), but the BSS 206 of a second wirelesscommunication carrier is not permitted. In another example, thepermission list for the subscription management service 104(N) may grantthird-party partner 210(1) access, but denies third-party partner 210(N)access. Thus, by comparing the entity identifier of the entity to theentity identifiers of entities that either has permission or is deniedpermission in the permission list, the eSIM profile management platform106 may determine whether the entity has access to the subscriptionmanagement service 104(N).

Assuming that the entity has access to the subscription managementservice 104, the eSIM profile management platform 106 may furthercompare the MNO identifier or the partner identifier associated witheSIM profile 214 to the entity identifier of the entity to determinewhether the entity has access to the eSIM profile 214. For example, thethird-party partner 210(1) may be trying to access the eSIM profile 214when the eSIM profile 214 has a partner identifier that matches theentity identifier of the third-party partner 210(N). In another example,the MNO identifier of the eSIM profile 214 may match an entityidentifier of the wireless communication carrier 102, but not the entityidentifier of a wireless communication carrier hosted by the carrier102. Thus, when there is a match between the entity identifier of theentity that initiated the request with respect to the eSIM profile 214and the MNO identifier or the partner identifier, the eSIM profilemanagement platform 106 may forward the request of the entity to thesubscription management service 104(N). In this way, the subscriptionmanagement service 104 may initiate a procedure that eventuallyprovisions the eUICC 202(N) of the user device 204(N) with the eSIMprofile 214.

However, if at any point the eSIM profile management platform 106determines that the request 212 with respect to the eSIM profile 214cannot be completed because of lack of access by the entity orunavailability of the eSIM profile 214, the eSIM profile managementplatform 106 may notify the entity that the request 212 of the entityhas failed. This means that the request 212 will not be forwarded by theeSIM profile management platform 106 to the subscription managementservice 104(N). In the scenario where the request 212 failed because ofthe unavailability of the eSIM profile 214, the eSIM profile managementplatform 106 may increase efficiency in the use of computing resourcesby not forwarding the request 212. This is because the subscriptionmanagement service 104(N) is able to forego a complicated procedure toprovision the eSIM profile 214 to the eUICC 202(N) by not receiving therequest, which would have eventually failed due to the unavailability.

In other embodiments, the request 212 may be a request to perform anaction on an eSIM profile that is already in an eUICC instead ofprovisioning the eSIM profile to an eUICC. For example, the request 212may be for activating the eSIM profile to obtain communication servicesfrom a wireless communication carrier, deleting the eSIM profile fromthe eUICC, or otherwise modify the eSIM profile. In such embodiments,the eSIM profile management platform 106 may compare the entityidentifier of the entity to a subscription management service permissionlist, a MNO identifier, and/or a partner identifier that are associatedwith the eSIM profile to determine whether the entity has access toperform the action in the same manner as described above. Furthermore,in other embodiments, the entity may make a request to perform an actionwith respect to a M2M EID. In such embodiments, the eSIM profilemanagement platform 106 may compare the entity identifier of the entityto a subscription management service permission list, a MNO identifier,and/or a partner identifier that are associated with the M2M EID todetermine whether the entity has access to perform the action on the M2MEID in a similar manner. The action may be in the form of reading,modifying, or deleting the M2M EID from a SM-SR or an eUICC of a userdevice. It will be appreciated that in other embodiments, each of thepermission check or access check can be performed independently of eachother. Thus, a subscription management service may be configured toperform one or more of these checks, rather than every check, in orderto grant or deny an entity access to an eSIM profile.

In some embodiments, the eSIM profile management platform 106 may havean audit function that monitors and corrects any errors in thedistribution of eSIM profiles to the subscription management services104(1)-104(N) by the eSIM profile vendors 108(1)-108N. For instance, aneSIM profile may have a subscription management service identifier thatindicates the profile is to be managed by a first subscriptionmanagement service, but the eSIM profile may be stored in a profile datastore of a second subscription management service. In such an instance,the audit function may transfer the eSIM profile from the data store ofthe second subscription management service to a datastore of the firstsubscription management service. In another instance, an eSIM profilemay have an indicator that shows that the profile is an M2M eSIMprofile, but the eSIM profile may be stored in a profile data store thatbelongs to a SM-DP+ of a subscription management service instead of aprofile data store of a SM-DP of the service. In such an instance, theaudit function may transfer the eSIM profile to the profile data storeof the SM-DP. These error correction transfers by the audit function mayalso trigger the data feed function 128 of a corresponding subscriptionmanagement service to send a service data feed to update the eSIMprofile management platform 106 of the changes.

Example Computing Device Components

FIG. 3 is a block diagram showing various components of one or moreillustrative computing devices that support the provision of servicedata feeds by subscription management services to an eSIM profilemanagement platform. The computing devices 300 may include acommunication interface 302, one or more processors 304, memory 306, andhardware 308. The communication interface 302 may include wirelessand/or wired communication components that enable the computing devices300 to transmit data to and receive data from other networked devices.The hardware 308 may include additional user interface, datacommunication, or data storage hardware. For example, the userinterfaces may include a data output device (e.g., visual display, audiospeakers), and one or more data input devices. The data input devicesmay include, but are not limited to, combinations of one or more ofkeypads, keyboards, mouse devices, touch screens that accept gestures,microphones, voice or speech recognition devices, and any other suitabledevices.

The memory 306 may be implemented using computer-readable media, such ascomputer storage media. Computer-readable media includes, at least, twotypes of computer-readable media, namely computer storage media andcommunications media. Computer storage media includes volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules, orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD), high-definition multimedia/data storage disks, orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other non-transmissionmedium that can be used to store information for access by a computingdevice. In contrast, communication media may embody computer-readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave, or other transmissionmechanism. In other embodiments, the computing devices 300 or componentsthereof may be virtual computing devices in the form of virtual machinesor software containers that are hosted in a computing cloud.

The computing devices 300 may implement various backend services andcomponents of the wireless communication carrier 102, such as thesubscription management services 104(1)-104(N), the eSIM profilemanagement platform 106, BSS 206, and/or BSS 208. The implementationinvolves the execution of software, applications, and/or modules thatinclude routines, program instructions, code segments, objects, and/ordata structures that perform particular tasks or implement particularabstract data types.

Example Processes

FIGS. 4-7 present illustrative processes 400-700 for enablingsubscription management service to provide service data feeds to an eSIMprofile management platform for the purpose of eSIM profile managementand control. Each of the processes 400-700 is illustrated as acollection of blocks in a logical flow chart, which represents asequence of operations that can be implemented in hardware, software, ora combination thereof. In the context of software, the blocks representcomputer-executable instructions that, when executed by one or moreprocessors, perform the recited operations. Generally,computer-executable instructions may include routines, code segments,programs, objects, components, data structures, and the like thatperform particular functions or implement particular abstract datatypes. The order in which the operations are described is not intendedto be construed as a limitation, and any number of the described blockscan be combined in any order and/or in parallel to implement theprocess. For discussion purposes, the processes 400-600 are describedwith reference to the architecture 100 of FIG. 1 and the operatingenvironment 200 of FIG. 2.

FIG. 4 is a flow diagram of an example process 400 for receiving servicedata feeds for M2M devices from a subscription management service. Atblock 402, a subscription management service may receive one or more M2MeSIM profiles from at least one eSIM profile vendor. In variousembodiments, the one or more M2M eSIM profiles may have been ordered bya wireless communication carrier 102, a wireless communication carrierthat is hosted by the wireless communication carrier 102, or athird-party partner of the wireless communication carrier 102. The oneor more M2M eSIM profiles may be delivered to the subscriptionmanagement service via a communication link between an eSIM profilevendor and the subscription management service.

At block 404, the subscription management service may load the one ormore M2M eSIM profiles into one or more SM-DP profile data stores of thesubscription management service. In various embodiments, the profiledata stores of each SM-DP may hold M2M eSIM profiles that are ordered bya single entity or different entities. At block 406, the subscriptionmanagement service may send at least one corresponding ICCID of the oneor more M2M eSIM profiles as loaded into the one or more SM-DP profiledata stores to the eSIM profile management platform 106 via a servicedata feed. In various embodiments, The ICCID of each M2M eSIM profile inthe service data feed may be accompanied by other associatedidentification information, such as a mobile network operator (MNO)identifier, a subscription management service identifier, a partneridentifier, and/or an EUM identifier. In some instances, the servicedata feed may further include an identifier of the specific SM-DP whoseprofile data store actually stored each M2M eSIM profile.

At block 408, the subscription management service may receive one ormore M2M EIDs from the at least one eSIM profile vendor. Each M2M EIDbelongs to an eUICC that is used by a M2M device, and a M2M eSIM profilemay be eventually deployed into the eUICC. At block 410, thesubscription management service may load the one or more M2M EIDs into aSM-SR EID data store.

At block 412, the subscription management service may send the one ormore M2M EIDs as loaded into the SM-SR data store to the eSIM profilemanagement platform 106. Each M2M EID may be accompanied by otherassociated identification information, such as a mobile network operator(MNO) identifier, a subscription management service identifier, apartner identifier, and/or an EUM identifier. In various embodiments,the service data feed for sending the one or more M2M EIDs may be thesame service data feed as the one used to send the one or more ICCIDs,or a different service data feed.

FIG. 5 is a flow diagram of an example process 500 for receiving servicedata feeds for consumer devices from a subscription management service.At block 502, the subscription management service may receive one ormore consumer eSIM profiles from one or more eSIM profile vendors.various embodiments, the one or more consumer eSIM profiles may havebeen ordered by a wireless communication carrier 102, a wirelesscommunication carrier that is hosted by the wireless communicationcarrier 102, or a third-party partner of the wireless communicationcarrier 102. The one or more consumer eSIM profiles may be delivered tothe subscription management service via a communication link between aneSIM profile vendor and the subscription management service.

At block 504, the subscription management service may load the one ormore consumer eSIM profiles into a SM-DP+ data store. In variousembodiments, the profile data stores the SM-DP+ may hold consumer eSIMprofiles that are ordered by a single entity or different entities. Atblock 506, the subscription management service may send at least onecorresponding ICCID of the one or more consumer eSIM profiles as loadedinto the SM-DP+ profile data store to the eSIM profile managementplatform 106 via a service data feed. In various embodiments, The ICCIDof each consumer eSIM profile in the service data feed may beaccompanied by other associated identification information, such as amobile network operator (MNO) identifier, a subscription managementservice identifier, a partner identifier, and/or an EUM identifier. Insome instances, the service data feed may further include an identifierof the specific SM-DP+ whose profile data store actually stored eachconsumer eSIM profile.

FIG. 6 is a flow diagram of an example process 600 for using the servicedata feeds from subscription management services to control access toeSIM profiles that are stored in a profile data store of a subscriptionmanagement service. At block 602, the eSIM profile management platform106 may receive a request from a requesting function of an entity toperform an action with respect to a particular eSIM profile that has aspecific ICCID. For example, the action may be sending the eSIM profilefor storage in an eUICC of a user device, activating the eSIM profilefor use to receive telecommunication services from the wirelesscommunication carrier, disabling the eSIM profile to terminate access ofthe user device to the telecommunication services, or deleting the eSIMprofile from the eUICC of the user device.

At block 604, the eSIM profile management platform 106 may determinebased on the specific ICCID whether the particular eSIM profile isloaded into a profile data store of a subscription management service.In instances where the eSIM profile is a M2M eSIM profile, the profilemay be loaded into a profile data store managed by a SM-DP of thesubscription management service. In instances where the eSIM profile isa consumer eSIM profile, the profile may be loaded into a profile datastore managed by a SM-DP+ of the subscription management service. Invarious embodiments, the determination may be made by comparing thespecific ICCID to ICCIDs of eSIM profiles that are recorded as beingloaded into the profile data stores of subscription management servicesin the centralized database 132. The data in the centralized database132 is extracted by the eSIM profile management platform 106 from one ormore service data feeds. At decision block 606, if the eSIM profilemanagement platform 106 determines that the particular eSIM profile withthe specific ICCID is not loaded (“no” at decision block 606), theprocess 600 may proceed to block 608. At block 608, the eSIM profilemanagement platform 106 may send an error message to the requestingfunction of the entity indicating that the action failed. In someembodiments, the error message may include a reason for the failure.

However, if the eSIM profile management platform 106 determines that theparticular eSIM profile with the specific ICCID is loaded (“yes” atdecision block 606), the process 600 may proceed to block 610. At block610, the eSIM profile management platform 106 may determine whether theentity has access to the subscription management service. In variousembodiments, the eSIM profile management platform 106 may use apermission list maintained for the subscription management service todetermine whether the entity has access to the subscription managementservice. At decision block 612, if the eSIM profile management platform106 determines that the entity has access to the subscription managementservice (“yes” at decision block 612), the process 600 may proceed toblock 614.

At block 614, the eSIM profile management platform 106 may determinewhether the entity has access to the particular eSIM profile based on apartner identifier or a MNO identifier associated with the particulareSIM profile. In instances where the entity is a third-party partner,the partner identifier of the third-party partner is compared to thepartner identifier associated with the particular eSIM profile todetermine if the identifiers match. Likewise, in instances where theentity is a wireless communication carrier, the identifier of thewireless communication carrier is compared to the MNO identifierassociated with the particular eSIM profile to determine if theidentifiers match. Accordingly, the entity is determined to have accesswhen the pair of compared identifiers match.

Accordingly, at decision block 616, if the eSIM profile managementplatform 106 determines that the entity has access to the particulareSIM profile (“yes” at decision block 616), the process 600 may proceedto block 618. At block 618, the eSIM profile management platform 106 mayforward the request for performing the action with respect to theparticular eSIM profile to the subscription management service. However,if the eSIM profile management platform 106 determines that the entitylacks access to the particular eSIM profile (“no” at decision block616), the process 600 may proceed to block 608. At block 608, the eSIMprofile management platform 106 may send an error message to therequesting function of the entity indicating that the action failed.

Returning to decision block 612, if the eSIM profile management platform106 determines that the entity lacks access to the subscriptionmanagement service (“no” at decision block 612), the process 600 mayproceed to block 608. Once again, at block 608, the eSIM profilemanagement platform 106 may send an error message to the requestingfunction of the entity indicating that the action failed.

FIG. 7 is a flow diagram of an example process 700 for using the servicedata feed information from subscription management services to controlaccess to M2M EIDs that are stored in an EID data store of asubscription management service. At block 702, the eSIM profilemanagement platform 106 may receive a request from a requesting functionof an entity to perform an action with respect to a particular M2M EID.In various embodiments, the action may be in the form of reading,modifying, or deleting the particular M2M EID from a SM-SR or an eUICCof a user device.

At block 704, the eSIM profile management platform 106 may determinebased on the specific ICCID whether the particular M2M ED is loaded intoan EID data store of a subscription management service. The EID datastore may be managed by a SM-SR of the subscription management service.In various embodiments, the determination may be made by comparing thespecific M2M EID to M2M EIDs that are recorded as being loaded into theEID data stores of subscription management services in the centralizeddatabase 132. The data in the centralized database 132 being extractedby the eSIM profile management platform 106 from one or more servicedata feeds. At decision block 706, if the eSIM profile managementplatform 106 determines that the particular M2M EID is not loaded (“no”at decision block 706), the process 700 may proceed to block 708. Atblock 708, the eSIM profile management platform 106 may send an errormessage to the requesting function of the entity indicating that theaction failed. In some embodiments, the error message may include areason for the failure.

However, if the eSIM profile management platform 106 determines that theparticular M2M EID is loaded (“yes” at decision block 706), the process700 may proceed to block 710. At block 710, the eSIM profile managementplatform 106 may determine whether the entity has access to thesubscription management service. In various embodiments, the eSIMprofile management platform 106 may use a permission list maintained forthe subscription management service to determine whether the entity hasaccess to the subscription management service. At decision block 712, ifthe eSIM profile management platform 106 determines that the entity hasaccess to the subscription management service (“yes” at decision block712), the process 700 may proceed to block 714.

At block 714, the eSIM profile management platform 106 may determinewhether the entity has access to the particular M2M EID based on apartner identifier or a MNO identifier associated with the particularM2M EID. In instances where the entity is a third-party partner, thepartner identifier of the third-party partner is compared to the partneridentifier associated with the particular M2M EID to determine if theidentifiers match. Likewise, in instances where the entity is a wirelesscommunication carrier, the identifier of the wireless communicationcarrier is compared to the MNO identifier associated with the particulareSIM profile to determine if the identifiers match. Accordingly, theentity is determined to have access when the pair of comparedidentifiers match.

Accordingly, at decision block 716, if the eSIM profile managementplatform 106 determines that the entity has access to the particular M2MEID (“yes” at decision block 716), the process 700 may proceed to block718. At block 718, the eSIM profile management platform 106 may forwardthe request for performing the action with respect to the particular M2MEID to the subscription management service. However, if the eSIM profilemanagement platform 106 determines that the entity lacks access to theparticular M2M EID (“no” at decision block 716), the process 700 mayproceed to block 708. At block 708, the eSIM profile management platform106 may send an error message to the requesting function of the entityindicating that the action failed.

Returning to decision block 712, if the eSIM profile management platform106 determines that the entity lacks access to the subscriptionmanagement service (“no” at decision block 712), the process 700 mayproceed to block 708. Once again, at block 708, the eSIM profilemanagement platform 106 may send an error message to the requestingfunction of the entity indicating that the action failed.

The ability of the eSIM profile management platform to receive servicedata feeds from multiple subscription management services allows theeSIM profile management platform to regulate access by various entitiesto the eSIM profiles managed by the services. The identificationinformation in the data feeds may be used by the platform to preventunauthorized access by an entity to a subscription management service,unauthorized access by a first entity to eSIM profiles that are orderedby a second entity. The data feeds may also reveal issues such as lateor failed transmittals of eSIM profiles to a subscription managementservice, or eSIM profiles being mistakenly transmitted to and stored bythe wrong subscription management service.

CONCLUSION

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as exemplary forms ofimplementing the claims.

What is claimed is:
 1. A computer-implemented method, comprising:receiving, at a subscription management service of a wirelesscommunication carrier, one or more consumer Embedded Subscriber IdentityModule (eSIM) profiles that are provided by at least one eSIM profilevendor; loading the one or more consumer eSIM profiles into aSubscription Manager Data Preparation Plus (SM-DP+) profile data storeof the subscription management service, each consumer eSIM profile fordeployment to an eUICC in a consumer device; and sending, via thesubscription management service, at least one corresponding IntegratedCircuit Card identifier (ICCID) of the one or more consumer eSIMprofiles as loaded into the SM-DP+ data store, and one or more mobilenetwork operator (MNO) identifiers or one or more partner identifiersassociated with the at least one corresponding ICCID, to an eSIM profilemanagement platform of the wireless communication carrier via a servicedata feed, the eSIM profile management platform providing a centralinterface for a plurality of entities to perform actions with respect toa plurality of consumer eSIM profiles and a plurality of eUICCIdentifiers (ElDs), wherein the eSIM profile management platform usesthe one or more MNO identifiers or the one or more partner identifiersincluded in the service data feed to determine whether an entity hasaccess to a particular consumer eSIM profile to perform the actions onthe particular consumer eSIM profile.
 2. The computer-implemented methodof claim 1, wherein an MNO identifier included in the service feedidentifies a corresponding wireless communication carrier that hasaccess to the particular consumer eSIM profile and a partner identifierincluded in the service feed identifies a third-party partner of thewireless communication carrier that has access to the particularconsumer eSIM profile.
 3. The computer-implemented method of claim 1,wherein the plurality of entities includes the wireless communicationcarrier, an additional wireless communication carrier hosted by thewireless communication carrier, or a third-party partner of the wirelesscommunication carrier.
 4. The computer-implemented method of claim 1,wherein the actions include sending the particular consumer eSIM profilefor storage in a particular eUICC of a particular consumer device,activating the particular consumer eSIM profile for use to receivetelecommunication services from the wireless communication carrier,disabling the particular consumer eSIM profile to terminate access ofthe particular consumer device to the telecommunication services, ordeleting the particular consumer eSIM profile from the particular eUICCof the particular consumer device.
 5. The computer-implemented method ofclaim 1, wherein a determination of whether the entity has access to theparticular consumer eSIM profile to perform an action on the particularconsumer eSIM profile is made by the eSIM profile management platformfollowing a request from the entity to perform the action on theparticular consumer eSIM profile.
 6. The computer-implemented method ofclaim 1, wherein the entity is the wireless communication carrier, anassociated wireless communication carrier that is hosted by the wirelesscommunication carrier, or a third-party partner of the wirelesscommunication carrier.
 7. The computer-implemented method of claim 6,wherein the associated wireless communication carrier is a mobilevirtual network operator (MVNO), a virtual network operator (VNO), or amobile other licensed operator (MOLO).
 8. One or more non-transitorycomputer-readable media of a subscription management service of awireless communication carrier storing computer-executable instructionsthat upon execution cause one or more processors to perform actscomprising: receiving one or more consumer Embedded Subscriber IdentityModule (eSIM) profiles that are provided by at least one eSIM profilevendor; loading the one or more consumer eSIM profiles into aSubscription Manager Data Preparation Plus (SM-DP+) profile data store,each consumer eSIM profile for deployment to an eUICC in a consumerdevice; and sending at least one corresponding Integrated Circuit Cardidentifier (ICCID) of the one or more consumer eSIM profiles as loadedinto the SM-DP+ data store, and one or more mobile network operator(MNO) identifiers or one or more partner identifiers associated with theat least one corresponding ICCID, to an eSIM profile management platformof the wireless communication carrier via a service data feed, the eSIMprofile management platform providing a central interface for aplurality of entities to perform actions with respect to a plurality ofconsumer eSIM profiles and a plurality of eUICC Identifiers (ElDs),wherein the eSIM profile management platform uses the one or more MNOidentifiers or the one or more partner identifiers included in theservice data feed to determine whether an entity has access to aparticular consumer eSIM profile to perform the actions on theparticular consumer eSIM profile.
 9. The one or more non-transitorycomputer-readable media of claim 8, wherein an MNO identifier includedin the service feed identifies a corresponding wireless communicationcarrier that has access to the particular consumer eSIM profile and apartner identifier included in the service feed identifies a third-partypartner of the wireless communication carrier that has access to theparticular consumer eSIM profile.
 10. The one or more non-transitorycomputer-readable media of claim 8, wherein the plurality of entitiesincludes the wireless communication carrier, an additional wirelesscommunication carrier hosted by the wireless communication carrier, or athird-party partner of the wireless communication carrier.
 11. The oneor more non-transitory computer-readable media of claim 8, wherein theactions include sending the particular consumer eSIM profile for storagein a particular eUICC of a particular consumer device, activating theparticular consumer eSIM profile for use to receive telecommunicationservices from the wireless communication carrier, disabling theparticular consumer eSIM profile to terminate access of the particularconsumer device to the telecommunication services, or deleting theparticular consumer eSIM profile from the particular eUICC of theparticular consumer device.
 12. The one or more non-transitorycomputer-readable media of claim 8, wherein a determination of whetherthe entity has access to the particular consumer eSIM profile to performan action on the particular consumer eSIM profile is made by the eSIMprofile management platform following a request from the entity toperform the action on the particular consumer eSIM profile.
 13. A systemthat hosts a subscription management service of a wireless communicationcarrier, comprising: one or more processors; and memory including aplurality of computer-executable components that are executable by theone or more processors to perform a plurality of acts, the plurality ofacts comprising: receiving one or more consumer Embedded SubscriberIdentity Module (eSIM) profiles that are provided by at least one eSIMprofile vendor; loading the one or more consumer eSIM profiles into aSubscription Manager Data Preparation Plus (SM-DP+) profile data store,each consumer eSIM profile for deployment to an eUICC in a consumerdevice; and sending at least one corresponding Integrated Circuit Cardidentifier (ICCID) of the one or more consumer eSIM profiles as loadedinto the SM-DP+ data store, and one or more mobile network operator(MNO) identifiers or one or more partner identifiers associated with theat least one corresponding ICCID, to an eSIM profile management platformof the wireless communication carrier via a service data feed, the eSIMprofile management platform providing a central interface for aplurality of entities to perform actions with respect to a plurality ofconsumer eSIM profiles and a plurality of eUICC Identifiers (ElDs),wherein the eSIM profile management platform uses the one or more MNOidentifiers or the one or more partner identifiers included in theservice data feed to determine whether an entity has access to aparticular consumer eSIM profile to perform the actions on theparticular consumer eSIM profile.
 14. The system claim 13, wherein anMNO identifier included in the service feed identifies a correspondingwireless communication carrier that has access to the particularconsumer eSIM profile and a partner identifier included in the servicefeed identifies a third-party partner of the wireless communicationcarrier that has access to the particular consumer eSIM profile.
 15. Thesystem of claim 13, wherein the plurality of entities includes thewireless communication carrier, an additional wireless communicationcarrier hosted by the wireless communication carrier, or a third-partypartner of the wireless communication carrier.
 16. The system of claim13, wherein the actions include sending the particular consumer eSIMprofile for storage in a particular eUICC of a particular consumerdevice, activating the particular consumer eSIM profile for use toreceive telecommunication services from the wireless communicationcarrier, disabling the particular consumer eSIM profile to terminateaccess of the particular consumer device to the telecommunicationservices, or deleting the particular consumer eSIM profile from theparticular eUICC of the particular consumer device.
 17. The system ofclaim 13, wherein a determination of whether the entity has access tothe particular consumer eSIM profile to perform an action on theparticular consumer eSIM profile is made by the eSIM profile managementplatform following a request from the entity to perform the action onthe particular consumer eSIM profile.
 18. The system of claim 17,wherein the entity is the wireless communication carrier, an associatedwireless communication carrier that is hosted by the wirelesscommunication carrier, or a third-party partner of the wirelesscommunication carrier.
 19. The one or more non-transitorycomputer-readable media of claim 8, wherein the entity is the wirelesscommunication carrier, an associated wireless communication carrier thatis hosted by the wireless communication carrier, or a third-partypartner of the wireless communication carrier.
 20. The one or morenon-transitory computer-readable media of claim 19, wherein theassociated wireless communication carrier is a mobile virtual networkoperator (MVNO), a virtual network operator (VNO), or a mobile otherlicensed operator (MOLO).